UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The Mainframe Product must perform verification of the correct operation of security functions upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days.


Overview

Finding ID Version Rule ID IA Controls Severity
V-68495 SRG-APP-000473-MFP-000371 SV-82985r1_rule Medium
Description
Without verification, security functions may not operate correctly and this failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights. This requirement applies to applications performing security functions and the applications performing security function verification/testing.
STIG Date
Mainframe Product Security Requirements Guide 2019-10-08

Details

Check Text ( C-69027r1_chk )
Examine the installation, configuration, and product documentation.

If the Mainframe Product verification of the correct operation of security functions, which may include the valid connection to an external security manager (ESM), is not performed upon product startup/restart, or by a user with privileged access, and/or every 30 days, this is a finding.
Fix Text (F-74611r1_fix)
If necessary, configure the Mainframe Product configuration and installation settings to perform verification of the correct operation of security functions, which may include the valid connection to an ESM, upon product startup/restart, or by a user with privileged access, and/or every 30 days.